fix(logging): route computeGlobalCache slow warn through log interceptor - #115
Merged
Conversation
The Cursor SDK console.warns a slow global-cache rebuild diagnostic (computeGlobalCache: slow ctx-..., meta=/totalMs: ...), which leaked raw into the TUI. Extend the existing console.warn interceptor in both the in-process transport and the sidecar child to recognize it and forward it as a structured opencode log with parsed numeric meta. The timestamp token varies in width, so the pattern accepts 2-3 digit hours.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Cursor SDK console.warns a slow global-cache rebuild diagnostic, which leaked raw into the TUI:
Extends the existing console.warn interceptor (same pattern as #111) in both transports:
src/provider/cursor-log-intercept.ts(in-process): newSLOW_CACHE_WARN_RE+parseSlowCacheWarnLine, routed viapluginLogwith parsed numeric metasrc/sidecar/agent-host.mjs(sidecar child): identical regex, forwarded as structuredev:"log"over JSONLNotes:
13:04:05.123vs113:26:23.106), so the pattern accepts 2-3 digit hours/aftermeta=is how the SDK prints its empty context object; the parser tolerates itTests: new in-process case (recognized line routed with meta, unrelated warn still passes through), new
emitSlowCacheWarnfake-SDK hook, sidecar end-to-end assertion.npm run typecheckclean,npm test622/622.